VM start error handling improvements and config to expose error to users#12894
Conversation
|
@blueorangutan package |
|
@sureshanaparti a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 4.22 #12894 +/- ##
============================================
- Coverage 17.60% 17.60% -0.01%
+ Complexity 15666 15661 -5
============================================
Files 5917 5917
Lines 531527 531556 +29
Branches 64982 64986 +4
============================================
- Hits 93584 93554 -30
- Misses 427389 427447 +58
- Partials 10554 10555 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ el10 ✔️ debian ✔️ suse15. SL-JID 17250 |
|
@blueorangutan test |
|
@kiranchavala a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-15745)
|
nvazquez
left a comment
There was a problem hiding this comment.
LGTM - thanks @sureshanaparti @kiranchavala



Description
This PR improves the VM start error handling and reports the error to admins. It introduces new config 'expose.errors.to.user' (default: false), the errors are reported to the users when the config is set to true.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?